chore(AGENTS.md): avoid by default adoption of agentic conventions#7177
chore(AGENTS.md): avoid by default adoption of agentic conventions#7177d3flex wants to merge 1 commit intoos-autoinst:masterfrom
Conversation
There are many reasons to not enforce use of AGENTS.md by default Here some of them: - let the user decide whether to use AI coding assistants at all - user might already have his/her own one - avoids conflicts - maintainance (prevent outdated conventions) - keeps the repo free of tooling-specific Signed-off-by: Ioannis Bonatakis <ybonatakis@suse.com>
|
Great PR! Please pay attention to the following items before merging: Files matching
This is an automatically generated QA checklist based on modified files. |
okurz
left a comment
There was a problem hiding this comment.
You can always combine personal preferences by putting them into local and home folder AGENTS.md, no need to disable the project one. If you see certain guidelines not generally applicable please address those specifically, don't move the whole file
But applies to the project and the user should have the free choice to decide whether to use it or not. There are also possible side effects and the rational approach is to not "enable" it by default. As a team member I have to remove it and makes my work unnecessarily harder |
I’d like to understand the side effects you're running into. Since AGENTS.md is just a passive text file, it shouldn't interfere with standard development workflows. |
it doesnt affect me personally and directly. My objection is that the project should not enable those capabilities by default. There are cases where I think we cant predict where this will be used and as an open source project should let the user decide if he wants it or not. As is now is opt-in by default. I list a few additional reasons in the commit. What might left out of it is exactly what it is not predictable and out of our control. it gives to any tooling to use it without us knowing now or in the future. So see my concern not as an objection about any specific instruction being wrong, which the content might be fine, but about this default opt-in behavior. Having it in the root means every contributor using an AI assistant gets the project's conventions injected automatically, whether they want them or not. isnt that some sort of inversion of the control and the opposite of what open source advocate? |
And I tried to explain why the very miniature set of rules included in the current AGENTS.md should be enabled by default. |
Martchus
left a comment
There was a problem hiding this comment.
To me this specific AGENTS.md file looks like a good default.
I am not questioning the context FYI |
There are many reasons to not enforce use of AGENTS.md by default Here some of them: